home *** CD-ROM | disk | FTP | other *** search
- Path: inforamp.net!ts32-15
- From: rmorin@inforamp.net (Randy Charles Morin)
- Newsgroups: comp.lang.c++
- Subject: Re: Coding Standards
- Date: Sun, 24 Mar 96 04:53:18 GMT
- Organization: MiddleWorld SoftWare
- Message-ID: <4j2kgg$svj@sam.inforamp.net>
- References: <4hj8ek$elu@sam.inforamp.net> <4hktar$5o2@galaxy.ucr.edu> <4hmqol$97j@abacus.abasoft.co.uk> <4hsg8r$pmm@sam.inforamp.net> <4i9o6j$p4l@daisy.pgh.wec.com> <4idskb$pc1@sam.inforamp.net> <314EBD08.43BC@virtus.com> <4io2i7$n9v@sam.inforamp.net> <4iuu6k$6a6@druid.borland.com>
- NNTP-Posting-Host: ts32-15.tor.inforamp.net
- X-Newsreader: News Xpress Version 1.0 Beta #4
-
- In article <4iuu6k$6a6@druid.borland.com>,
- pete@borland.com (Pete Becker) wrote:
- >Unfortunately, if you don't follow guidelines like this, you will miss your
- >subsequent maintenance deadlines by many years. You'll spend all your time
- >tracking down mysterious failures that arise when you try to enhance the
- >program, rather than spending time on the enhancements themselves.
-
- But if you follow these guidelines, your initial release will miss your
- subsequent maintenance deadlines. You have to be reasonable in these
- situations. Why not make the standard that if you add a data member that may
- cause the default copy constructor to produce erroneous results, then make one
- explicitly? This way you only have to write them when you need to and you
- have the same end result.
-
-
- Agrivar
-
- aka Randy Charles Morin
- MiddleWorld SoftWare
- Canada: 1-800-363-3780
- Other: 905-279-2087
-